-
Notifications
You must be signed in to change notification settings - Fork 477
Update transaction pipelining docs re: parallelism #20314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update transaction pipelining docs re: parallelism #20314
Conversation
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
ce0234e to
7ebf84b
Compare
|
@stevendanna as the reviewer of #19601 (buffered writes) are you also a good reviewer for this update to the transaction pipelining docs? specifically we're correcting some misleading statements about performance that led to a customer filing a support issue (see DOC-8591 for details) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, this looks good to me.
One small note is that there seems to be some part-of-speech disagreement in the list of work that is still per-statement.
Thanks for pointing this out, I revised that whole paragraph a bit to simplify it overall as well as hopefully fix the mismatched part of speech phrasing in the list of per-statement work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't sure if "intent writes" (line 367 in src/current/v25.4/architecture/transaction-layer.md) was a typo or if that's just a synonymous term for "write intents."
Otherwise LGTM.
Fixes DOC-8591 Previously, we stated that the cost of writes is ~`O(1)` in the number of inserts, which is wrong. The reality is that despite the parallelism introduced by pipelining, there is other work that happens for each SQL statement write that does not come "for free". NB. These changes are ported to all supported versions v23.2+
ah thanks! reversed Thank you both for the reviews - backporting these changes to docs for all supported versions |
b421d22 to
7305d6a
Compare
Fixes DOC-8591
Specifically, we state that the cost of writes is ~
O(1)in the number of inserts, which is misleading. The reality is that despite the parallelism introduced by pipelining, there is other work that happens for each write that does not come "for free".